Use of gesture-based nfc interaction to trigger device functionality

ABSTRACT

An automated method is provided for activating a function in a mobile interface device using near field communication (NFC). In the method, the mobile interface device receives a sequence of NFC transmissions from one or more NFC transmitters. Each NFC transmitter has an associated identifier and each NFC transmission is triggered by a spatial interaction between the mobile interface device and one of the one or more NFC transmitters. The mobile interface device determines whether the sequence of NFC transmissions meets matching criteria for one of a plurality of predetermined transmission sequences. Responsive to a determination that the sequence of NFC transmissions meets matching criteria for one of the predetermined transmission sequences, the mobile interface device determines the predetermined function associated with the one of the predetermined transmission sequences and initiates the predetermined function.

This application claims priority to U.S. Provisional Patent Application 62/679,571, filed Jun. 1, 2018, the complete disclosure of which is incorporated herein by reference.

FIELD OF THE INVENTION

This application relates generally to communication with contactless interfaces (e.g., radio-frequency identification (RFID) tags and other near field communication (NFC) devices) and device enhancement, and, more particularly, to the use of gesture-based interaction of a user device with an NFC device to activate a user device function.

BACKGROUND OF THE INVENTION

In the related art, the functionality of contactless interface points and readers (e.g., RFID and other NFC devices) typically provides for the acquiring of a single source of static information. This static information provision does not provide for nuanced device and function management. Accordingly, there is a need for improved systems and methods to provide enhancements to contactless interface points, contactless interface point functionality, and contactless interface point readers, including user devices. Embodiments of the present disclosure are directed to these and other considerations.

SUMMARY OF THE INVENTION

An illustrative aspect of the invention provides an automated method of activating a function in a mobile interface device using near field communication (NFC). The method comprises receiving, by the mobile interface device, a sequence of NFC transmissions from one or more NFC transmitters. Each NFC transmitter has an associated identifier and each NFC transmission is triggered by a spatial interaction between the mobile interface device and one of the one or more NFC transmitters. The method further comprises determining, by the mobile interface device, whether the sequence of NFC transmissions meets matching criteria for one of a plurality of predetermined transmission sequences. Responsive to a determination that the sequence of NFC transmissions meets matching criteria for one of the predetermined transmission sequences, the mobile interface device determines the predetermined function associated with the one of the predetermined transmission sequences and initiates the predetermined function.

Another aspect of the invention provides a mobile interface device comprising a data processor and a near field communication (NFC) interface configured to establish NFC communication with any of a plurality of NFC transmitting devices when the user interface device is placed within a communication range of said any of a plurality of NFC transmitting devices. The mobile interface device further comprises a user interface comprising at least a user input device and a display and a memory accessible by the data processor. The memory has stored therein instructions for executing any of a plurality of device functions, each device function being associated with a different predetermined NFC transmission sequence. The memory further has an NFC application including instructions for the data processor to receive an NFC transmission for each NFC communication established by the NFC interface. The NFC application includes further instructions to monitor sequential NFC transmissions to determine if a sequence of received NFC transmissions meets matching criteria for one of the predetermined transmission sequences. If a received sequence of NFC transmissions meets the matching criteria for one of the predetermined transmission sequences, the NFC application initiates the predetermined function associated with the matched predetermined transmission sequence.

Another aspect of the invention provides a near field communication (NFC) system comprising an array of NFC transmitting devices, each having an associated identifier. The NFC system further comprises a plurality of user interface devices. Each user interface device comprises a data processor, a user interface, an NFC interface and a memory accessible by the data processor. The NFC interface is configured to establish NFC communication with any of the array of NFC transmitting devices when the user interface device is placed within a communication range of said any of a plurality of NFC transmitting devices. The memory has stored thereon instructions for executing each of a plurality of device functions. Each device function is associated with a different predetermined NFC transmission sequence. The memory also has stored thereon an NFC application including instructions for the data processor to receive an NFC transmission for each NFC communication established by the NFC interface and monitor sequential NFC transmissions to determine if a sequence of received NFC transmissions meets matching criteria for one of the predetermined transmission sequences. If a received sequence of NFC transmissions meets the matching criteria for one of the predetermined transmission sequences, the NFC application initiates the predetermined function associated with the matched predetermined transmission sequence.

BRIEF DESCRIPTION OF THE DRAWINGS

The invention can be more fully understood by reading the following detailed description together with the accompanying drawings, in which like reference indicators are used to designate like elements, and in which:

FIG. 1 is an example block diagram representing a system environment that may implement one or more aspects of the present disclosure;

FIG. 2 is a component diagram of an example service provider terminal;

FIG. 3A illustrates a system environment for implementing certain aspects of the present disclosure;

FIG. 3B is an example flowchart of a method of the present disclosure;

FIG. 4A illustrates a system for activating the NFC capability of a user device according to an embodiment of the disclosure;

FIG. 4B is a flowchart of a method of activating an NFC application on a mobile interface device according to an embodiment of the disclosure;

FIG. 5A is a schematic representation of an an NFC communication system 500 according to an embodiment of the invention;

FIG. 5B is a schematic representation of an array of NFC devices usable in conjunction with methods of the invention;

FIG. 5C is a flow diagram for a method according to an embodiment of the invention;

FIG. 6A illustrates a system environment for implementing certain aspects of the present disclosure;

FIG. 6B is an example flowchart of a method of the present disclosure;

FIG. 7A illustrates a rules-based NFC communication system according to an embodiment of the disclosure;

FIG. 7B is a flow diagram of a method of activating a transaction function in a transaction processing device according to an embodiment of the disclosure;

FIG. 7C is a flow diagram of a method of initiating a transaction function in a transaction processing device according to an embodiment of the disclosure;

FIG. 8A illustrates a system environment for implementing certain aspects of the present disclosure;

FIG. 8B is an example flowchart of a method of the present disclosure; and

FIG. 9 is a computer architecture block diagram according to an example embodiment.

DETAILED DESCRIPTION OF THE INVENTION

Some implementations of the disclosed technology will be described more fully with reference to the accompanying drawings. This disclosed technology may, however, be embodied in many different forms and should not be construed as limited to the implementations set forth herein. The components described hereinafter as making up various elements of the disclosed technology are intended to be illustrative and not restrictive. Many suitable components that would perform the same or similar functions as components described herein are intended to be embraced within the scope of the disclosed electronic devices and methods. Such other components not described herein may include, but are not limited to, for example, components developed after development of the disclosed technology.

It is also to be understood that the mention of one or more method steps does not preclude the presence of additional method steps or intervening method steps between those steps expressly identified. Similarly, it is also to be understood that the mention of one or more components in a device or system does not preclude the presence of additional components or intervening components between those components expressly identified.

Although RFIDs, RFID stickers, RFID devices, RFID kiosks, etc., are generally used herein, these are merely examples. One of ordinary skill will recognize that, in light of the present disclosure, the RFID technology may be substituted or augmented with various types of contactless or wireless technologies. As non-limiting examples, various aspects of the present disclosure may utilize one or more of NFC tags, RFID stickers, and NXP MIFARE stickers, image codes (e.g., one-or two dimensional barcodes or QR codes), as well as interface points for different frequency readers (e.g., readers attuned to non-traditional contactless interface point tunings), and contactless interface points designed for different technologies (e.g., sonic readers or X-ray readers) may be used in addition to or in place of RFID devices.

FIG. 1 illustrates a system environment 100 in which one or more aspects of the present disclosure may be implemented. System environment 100 may include one or more of a user device 110, a service provider terminal 120, a service provider database system 130, a merchant terminal 140, a merchant database system 150, a beacon 170, an NFC device 180, and a network 190. In some cases, system environment 100 may include one or more of each of user devices 110, service provider terminals 120, service provider database systems 130, merchant terminals 140, merchant database systems 150, beacons 170, NFC devices 180, and networks 190. A non-limiting example of a computer system architecture that can implement one or more of user device 110, service provider terminal 120, service provider database system 130, merchant terminal 140, merchant database system 150, and beacon 170 will be described below in greater detail with reference to FIG. 9.

User device 110 may include, as non-limiting examples, a mobile interface device (e.g., a smart phone, tablet computer, smart wearable device, portable laptop computer, voice command device, or other mobile computing device) or a stationary computing device (e.g., a stationary desktop or other stationary computer). In some embodiments, user device 110 may be configured to interact with one or more of service provider terminal 120, service provider database system 130, merchant terminal 140, merchant database system 150, beacon 170, and NFC device 180, either directly or over network 190. User device 110 and may be equipped with a display, speakers or other auditory devices, tactile simulators, haptic sensors, cameras, light projectors, input devices, distance measuring equipment, 3D scanners, IR sensors, microphones, orientation/position/location sensors, accelerometers, and other devices.

An exemplary embodiment of service provider terminal 120 is shown in more detail in FIG. 2. User device 110, service provider database system 130, merchant terminal 140, merchant database system 150, and beacon 170 may have a similar structure and components that are similar to those described with respect to service provider terminal 120. As shown, service provider terminal 120 may include a processor 210, an input/output (“I/O”) device 220, a memory 230 containing an operating system (“OS”) 240 and a program 250. For example, service provider terminal 120 may be a single server or may be configured as a distributed computer system including multiple servers or computers that interoperate to perform one or more of the processes and functionalities associated with the disclosed embodiments. In some embodiments, the service provider terminal 120 may further include a peripheral interface, a transceiver, a mobile network interface in communication with the processor 210, a bus configured to facilitate communication between the various components of the service provider terminal 120, and a power source configured to power one or more components of the service provider terminal 120.

A peripheral interface may include the hardware, firmware and/or software that enables communication with various peripheral devices, such as media drives (e.g., magnetic disk, solid state, or optical disk drives), other processing devices, or any other input source used in connection with the instant techniques. In some embodiments, a peripheral interface may include a serial port, a parallel port, a general purpose input and output (GPIO) port, a game port, a universal serial bus (USB), a micro-USB port, a high definition multimedia (HDMI) port, a video port, an audio port, a Bluetooth™ port, a near-field communication (NFC) port, another like communication interface, or any combination thereof

In some embodiments, a transceiver may be configured to communicate with compatible devices and ID tags when they are within a predetermined range. A transceiver may be compatible with, for example, one or more of: radio-frequency identification (RFID), near-field communication (NFC), Bluetooth™, low-energy Bluetooth™ (BLE), WiFi™, ZigBee™, Z-Wave™, ambient backscatter communications (ABC) protocols or similar technologies.

A mobile network interface may provide access to a cellular network, the Internet, or another wide-area network. In some embodiments, a mobile network interface may include hardware, firmware, and/or software that allows the processor(s) 210 to communicate with other devices via wired or wireless networks, whether local or wide area, private or public, as known in the art. A power source may be configured to provide an appropriate alternating current (AC) or direct current (DC) to power components.

Processor 210 may include one or more of a microprocessor, microcontroller, digital signal processor, co-processor or the like or combinations thereof capable of executing stored instructions and operating upon stored data. Memory 230 may include, in some implementations, one or more suitable types of memory (e.g. such as volatile or non-volatile memory, random access memory (RAM), read only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, flash memory, a redundant array of independent disks (RAID), and the like), for storing files including an operating system, application programs (including, for example, a web browser application, a widget or gadget engine, and or other applications, as necessary), executable instructions and data. In one embodiment, the processing techniques described herein are implemented as a combination of executable instructions and data within the memory 230.

Processor 210 may be one or more known processing devices, such as, but not limited to, a microprocessor from the Pentium™ family manufactured by Intel™ or the Turion™ family manufactured by AMD™. Processor 210 may constitute a single core or multiple core processor that executes parallel processes simultaneously. For example, processor 210 may be a single core processor that is configured with virtual processing technologies. In certain embodiments, processor 210 may use logical processors to simultaneously execute and control multiple processes. Processor 210 may implement virtual machine technologies, or other similar known technologies to provide the ability to execute, control, run, manipulate, store, etc. multiple software processes, applications, programs, etc. One of ordinary skill in the art would understand that other types of processor arrangements could be implemented that provide for the capabilities disclosed herein.

Service provider terminal 120 may include one or more storage devices configured to store information used by processor 210 (or other components) to perform certain functions related to the disclosed embodiments. In one example, service provider terminal 120 may include memory 230 that includes instructions to enable processor 210 to execute one or more applications, such as server applications, network communication processes, and any other type of application or software known to be available on computer systems. Alternatively, the instructions, application programs, etc. may be stored in an external storage or available from a memory over a network. The one or more storage devices may be a volatile or non-volatile, magnetic, semiconductor, tape, optical, removable, non-removable, or other type of storage device or tangible computer-readable medium.

In one embodiment, service provider terminal 120 may include memory 230 that includes instructions that, when executed by processor 210, perform one or more processes consistent with the functionalities disclosed herein. Methods, systems, and articles of manufacture consistent with disclosed embodiments are not limited to separate programs or computers configured to perform dedicated tasks. For example, service provider terminal 120 may include memory 230 that may include one or more programs 250 to perform one or more functions of the disclosed embodiments. Moreover, processor 210 may execute one or more programs 250 located remotely from system 100. For example, system 100 may access one or more remote programs 250, that, when executed, perform functions related to disclosed embodiments.

Memory 230 may include one or more memory devices that store data and instructions used to perform one or more features of the disclosed embodiments. Memory 230 may also include any combination of one or more databases controlled by memory controller devices (e.g., server(s), etc.) or software, such as document management systems, Microsoft™ SQL databases, SharePoint™ databases, Oracle™ databases, Sybase™ databases, or other relational databases. Memory 230 may include software components that, when executed by processor 210, perform one or more processes consistent with the disclosed embodiments. In some embodiments, memory 230 may include one or more databases 260, for storing related data to enable service provider terminal 120 to perform one or more of the processes and functionalities associated with the disclosed embodiments.

Service provider terminal 120 may also be communicatively connected to one or more memory devices (e.g., databases (not shown)) locally or through a network. The remote memory devices may be configured to store information and may be accessed and/or managed by service provider terminal 120. By way of example, the remote memory devices may be document management systems, Microsoft™ SQL databases, SharePoint™ databases, Oracle™ databases, Sybase™ databases, or other relational databases. Systems and methods consistent with disclosed embodiments, however, are not limited to separate databases or even to the use of a database.

Service provider terminal 120 may also include one or more I/O devices 220 that may comprise one or more interfaces for receiving signals or input from devices and providing signals or output to one or more devices that allow data to be received and/or transmitted by service provider terminal 120. For example, service provider terminal 120 may include interface components, which may provide interfaces to one or more input devices, such as one or more keyboards, mouse devices, touch screens, track pads, trackballs, scroll wheels, digital cameras, microphones, sensors, and the like, that enable service provider terminal 120 to receive data from one or more users (such as via user terminal 120).

In exemplary embodiments of the disclosed technology, service provider terminal 120 may include any number of hardware and/or software applications that are executed to facilitate any of the operations. The one or more I/O interfaces may be utilized to receive or collect data and/or user instructions from a wide variety of input devices. Received data may be processed by one or more computer processors as desired in various implementations of the disclosed technology and/or stored in one or more memory devices.

While service provider terminal 120 has been described as one form for implementing the techniques described herein, those having ordinary skill in the art will appreciate that other, functionally equivalent techniques may be employed. For example, as known in the art, some or all of the functionality implemented via executable instructions may also be implemented using firmware and/or hardware devices such as application specific integrated circuits (ASICs), programmable logic arrays, state machines, etc. Furthermore, other implementations of the terminal 120 may include a greater or lesser number of components than those illustrated.

Service provider database 130 may have one or more processors 132 and one or more memory 134, which may be any suitable repository of merchant data. Service provider 130 may be located at a service provider database 130 location, off-site at another service provider location, or at a third-party location. Information stored in memory 134 may be accessed (e.g., retrieved, updated, and added to) via network 190 by one or more devices (e.g., service provider terminal 120). Memory 134 may store information relating to, as non-limiting examples, a user profile, RFID and/or beacon configurations, and merchant information.

Merchant terminal 140 may have one or more POS devices 142 that communicate with one or more devices (e.g., user device 110) via network 190. In some embodiments, POS device 162 may communicate with one or more devices (e.g., user device 110) using short-range communication.

Merchant database 150 may have one or more processors 152 and one or more memory 154, which may be any suitable repository of merchant data. Merchant database 150 may be located at the POS location, off-site at another merchant location, or at a third-party location. Information stored in memory 154 may be accessed (e.g., retrieved, updated, and added to) via network 190 by one or more devices (e.g., service provider terminal 120) of system environment 100. Memory 154 may store information relating to products and services offered by merchants such as pricing, quantity, availability, discounts, reviews, and any other such generally available information that a consumer may utilize in making a purchasing decision. In some embodiments, memory 154 may also include location information associated with products and services that identifies the location(s) that a particular product or service is available for purchase. In some embodiments, the location information may include an identification of a particular store, terminal, or kiosk that the product or service may be purchased from.

Beacon 170 may output a signal (e.g., constantly, periodically, or randomly). In some embodiments, one or more of the beacons 170 may be positioned proximate a POS location and configured to output a signal to one or more other devices of the system 100 that are within a predetermined range of the respective beacon 170 (e.g., to user device 110 of a customer walking through a store). The signal may include preset information. For example, the information may be detected by the user device 110 (e.g., an application executing on the user device 110), which triggers the user device 110 to perform some action. In some cases, beacon 170 may be modified (e.g., to change the information transmitted or the transmission pattern/strength). Beacon 170 may be connected to network 190, and may be, as a non-limiting example, modified by service provider terminal 120.

The signal of a beacon 170 may contain two numbers referred to herein as the beacon's major and minor identifiers. These identifiers may be used to identify the beacon's location. In particular applications, the beacon's major identifier may be associated with a relatively large area or building (e.g., a store or other business) in which multiple beacons may be positioned. In such applications, the minor identifier may be associated with a smaller area (e.g., a retail department) that is within the larger area and within which the particular beacon is located. In some applications, the beacon's signal may also include a source identifier that identifies the controlling entity (e.g., a merchant) associated with the beacon. As is discussed in more detail below, the user device 110 may be configured, not only to detect the signal from a beacon 170, but to determine a signal strength as well. This may allow the determination of a distance from the beacon 170.

NFC device 180 may be any form of NFC transmitter and/or receiver. In particular embodiments, the NFC device 180 may be or comprise an RFID transmitter or receiver. Such a device may be active or passive and may be in communication with other RFID-capable devices in the system 100. In some embodiments, the NFC device 180 may be configured to broadcast predetermined information, thereby acting as an NFC transmitter configured to communicate with an NFC reader. For example, user device 110 may receive (e.g., using an application) transmitted information from an NFC device 180. In some cases, user device 110 may then transmit the received information to service provider terminal 120. Service provider terminal 120 may reference data stored in service provider database system 130 to determine what trigger NFC device 180 represents. For example, in some cases, NFC device 180 may be associated with a location either directly (embedded NFC device information) or indirectly (NFC device information is a location pointer), and confirmation of user device 110 being within a predetermined range of that location may trigger one or more predetermined actions or steps of a method described herein. In some cases, service provider terminal 120 may transmit the interpretation of the data back to user device 110.

While the NFC device 180 may often be an RFID device, this is merely an example, and one of ordinary skill will recognize that various different types of contactless interface points may be utilized in system environment 100. For example, one or more of NFC tags, RFID stickers, and NXP MIFARE stickers, as well as interface points for different frequency readers (e.g., readers attuned to non-traditional contactless interface point tunings), non IoT devices, and contactless interface points designed for different technologies (e.g., sonic readers or X-ray readers) may be used within system environment 100. User device 110 may receive and read transmissions from the various types of contactless interface points in similar manner as discussed herein, or as modified in a manner understood by one of ordinary skill in light of the present disclosure. The user device 110 may utilize the information gathered from the various NFC devices 180, for example, as “location-based IDs,” as triggers to perform a function, or to contact a database for more information, as will be discussed in greater detail below.

Network 190 may be of any suitable type, including individual connections via the internet such as cellular or WiFi networks. In some embodiments, network 190 may connect terminals using direct connections such as radio-frequency identification (RFID), near-field communication (NFC), Bluetooth′, low-energy Bluetooth′ (BLE), WiFi™, ZigBee′, Z-Wave′, ambient backscatter communications (ABC) protocols, USB, or LAN. Because the information transmitted may be personal or confidential, security concerns may dictate one or more of these types of connections be encrypted or otherwise secured. In some embodiments, however, the information being transmitted may be less personal, and therefore the network connections may be selected for convenience over security.

Location based services (LBS) are often dependent on GPS and user-confirmed tracking input. In the related art, users may be prompted by the LBS to select their locations when GPS is unavailable. For example, GPS is often unreliable when inside a building (e.g., inside a mall), so LBSs rely on user-selected locations to determine what store a user is in. This can lead to LBS location requests out of context to where the LBSs would be useful. Thus, users may be inconvenienced by inconsistent LBS availability, and annoyed by unwarranted LBS requests. Accordingly, users may deactivate, deactivate, or otherwise limit the LBS and related capabilities, which decreases user engagement and LBS utility. Accordingly, certain aspects of the present disclosure relate to the use of contactless interface points (e.g., RFIDs) to provide location information, which may be used to improve LBS services.

FIG. 3A illustrates a system environment for implementing certain aspects of the present disclosure. In the system environment of FIG. 3A, a user device (e.g., user device 110, which may be a mobile device) operated by a user, an NFC device (e.g., an RFID sticker), a network (e.g., network 190), and a database (e.g., service provider database system 130) may interact. The user may operate the user device to execute an RFID reader application, and the user may move the user device near the RFID sticker. The user device may interpret the information from the RFID sticker and provide the information to the database over the network. The information may include location information (e.g., coordinates, store name and number, geo-coding, encoded location information, or encrypted location information) or RFID information ((e.g., an RFID specifier that is associated with a geographic location in the database). With RFID sticker systems embedded in environments, users may easily “opt-in” to LBS, for example by tapping or otherwise reading RFID touch points with their devices. This allows location-based data to be generated outside of traditional GPS system networks and enables contextual “opt-in” opportunities relevant to the user's contexts. For example, after checking in by tapping on the RFID sticker (or otherwise reading or scanning a contactless interface point), an LBS may provide the user device information about special events nearby (e.g., photos with Santa or limited-time deals).

In some cases, reading the device may not operate as a strict opt-in to an LBS (i.e., may not have include the user electing to receive future messages of LBS services), but rather provide a user initiated call for information (e.g., from a database). Accordingly, instead of the traditional LBS PUSH content/marketing, there may be provided LBS PULL content/marketing (e.g., a user has precise control over when, where and how they receive the content or marketing materials). For example, a user can “initiate a call” for discount coupons or customer service at precise location by using the user device to read the contactless interface point, and the database may trigger action rules that send out a 10% off discount to customer account or send out a notification to customer service, so customer service can contact the customer at this specify location.

FIG. 3B is an example flowchart of a method of the present disclosure. The user taps an RFID touchpoint with the user device. For example, the user may move the mobile device within a predefined range of RFID sticker. The user device reads the RFID with NFC. For example, user device may constantly or regularly poll for RFID information. The user device sends the RFID information to the network. The RFID information may include location information of the RFID. The network stored the RFID location information in the database associated with the user profile. In some cases, an external device (e.g., service provider terminal 120) may utilize the RFID location information to push services or functions to the user device. The database may also relay the location information back to the user device or an application executing on the user device (e.g., if the location information is encoded or otherwise not easily determinable by the RFID information). The user device may then perform actions, execute applications, and/or initialize functions based on the location information. In some cases, user location history may be captured, for example, for future behavioral analysis and/or to correlate with transaction locations to identify fraudulent behaviors.

As a non-limiting example, consider two users “A” and “B” in a same location at the same time. Both users use their user devices to read contactless interface points at the location and provide the location information to the database. The database determines location-based rules and user preferences, and then the database sends respective triggers (e.g., different triggers) to the user devices. Accordingly, User A may receive a discount, and User B might be provided new product introduction, despite reading a same contactless interface point at a same time.

In many instances, a user's mobile device may require an action to place it in an active state for receiving NFC transmissions. By not having a default active state, a hurdle is placed between the user and ready NFC communication. This can create inefficiencies in, for example, reading RFID signals using a mobile interface device (e.g., a smartphone). An aspect of the present invention is to make use of beacon technology to automatically activate and deactivate an NFC reader of a user device (particularly, a mobile interface device) without a required action on the part of the user. This provides significant improvements in efficiency and other functional advantages over the related art.

FIG. 4A illustrates a system environment 400 for certain aspects of the present invention. In the system environment of FIG. 4A, a user device 410 (e.g., a mobile interface device) operated by a user, one or more NFC devices 480 (e.g., RFID tags or other transmission devices), and one or more beacons 470. In the descriptions that follow, the system environment 400 is a retail environment in the form of a retail store having multiple sales departments. It will be understood, however, that the invention is not restricted to the retail environment. Each beacon 470 is disposed within the store in the area of one of the sales departments (or another area) and has a major location identifier associated with the retail store location and a minor location identifier associated the sales department (or other area) location. Each beacon 470 is configured to broadcast a signal comprising its major and minor identifiers. In some embodiments, the beacon signal may also comprise a source identifier associated with the beacon-controlling entity (e.g., the merchant or parent company associated with the retail store). The beacons 470 will typically have an associated range volume throughout which the broadcast signal strength exceeds a level detectable by typical user devices.

The NFC devices 480 may be any NFC enabled transmitter and/or receiver positioned within the retail store. Each NFC device 480 may be specifically configured for communication with NFC-enabled user devices. In some embodiments, some or all of the NFC devices 480 may be part of or associated with merchant terminals and/or POS devices within the retail store.

As shown in FIG. 4A, the user device 410 includes an on-board data processor 411 in communication with a memory module 413, a user interface 414, a communication interface 412, a beacon monitor 415, and an NFC interface 419. The data processor 411 can include a microprocessor and associated processing circuitry, and can contain additional components, including processors, memories, error and parity/CRC checkers, data encoders, anticollision algorithms, controllers, command decoders, security primitives and tamper-proofing hardware, as necessary to perform the functions described herein. The memory 413 can be a read-only memory, write-once read-multiple memory or read/write memory, e.g., RAM, ROM and EEPROM, and the user device 410 can include one or more of these memories.

The user interface 414 includes a user input mechanism, which can be any device for entering information and instructions into the user device 410, such as a touch-screen, keyboard, mouse, cursor-control device, microphone, stylus, or digital camera. The communication interface 412 is in data communication with the data processor 411 and is configured to establish and support wired or wireless data communication capability for connecting the device 410 to a communication network. The beacon monitor 415 is in data communication with the data processor 411 and is configured to receive and process transmissions from the one or more beacons 470 via an antenna 416 or other beacon signal receiver, convert the signal to digital data, and forward the digital data to the data processor 411. The beacon monitor 415 may further be configured to determine the signal strength of a received transmission. The NFC interface 419 is in data communication with the data processor 411 and is configured for establishing near field communication with any of the one or more NFC devices 480. Information received via the NFC interface 419 is forwarded to the data processor 411.

In various embodiments of the invention, the memory 413 may have stored therein one or more applications each comprising a plurality of instructions usable by the data processor 411 to conduct and/or monitor transactions between the user device 410 and merchant terminals, service providers, and transaction processing servers. These applications may include instructions usable by the data processor 411 to identify transaction events, store event data in the memory 413, and communicate event data to a transaction processor and/or a transaction monitoring system. Some applications may also include instructions relating to receiving and interpreting instructions from the transaction processor or transaction monitoring system.

The memory 413 has stored therein an NFC application comprising a plurality of instructions usable by the data processor 411 to establish communication with an NFC transmission device via the NFC interface 419. The NFC application is configured to have an active state in which placement of the user device 410 in contact with or within a predetermined NFC communication distance of an NFC device 480 causes the NFC device 480 to transmit information receivable via the NFC interface 419. The NFC application is further configured to have a passive state in which NFC communication is not established when the user device 410 is placed in contact with or within the predetermined NFC communication distance of an NFC device 480.

The memory 413 also has stored therein a beacon monitoring application. The beacon monitoring application is operable as a background application comprising a plurality of instructions usable by the data processor 411 to receive and process signal data from the beacon monitor 415. The beacon monitoring application is configured, in particular, to determine from the signal data, location identity information for the beacon 470 broadcasting the signal from which the signal data is derived.

In an exemplary scenario, a user may cause the user device 410 to execute the beacon monitoring application in the background to detect beacons 470. When the user enters the broadcast area (or “zone”) of a recognized beacon 470, the beacon is detected by the user device 410 and the NFC reader application on the user device is activated. The user may then use the user device 410 to interact with NFC transmitters within the broadcast area. This would allow, for example, instant reading of RFID information at a given location or touchpoint. Once the RFID information has been read, the user device 410 may operate in accordance with the discussion of other example embodiments herein. For example, the user device may output location information to a network, launch an application, launch a mobile function, or execute a transaction When the user leaves the beacon's broadcast area, immediately or shortly thereafter, the NFC application will revert to its passive state. In some instances, leaving the beacon zone may trigger an additional or alternative action of the user device (e.g., an action in addition to or instead of transitioning to the NFC passive state). For example, if the beacon zone is in a store, leaving the beacon zone without making a purchase may trigger a discount request from the user device.

FIG. 4B illustrates a method M400 of activating an NFC application in a user device 410 in accordance with an embodiment of the invention. The user device 410 may be, in particular, a mobile interface device such as a smart phone or tablet or other mobile device. At S410, a transmission from a beacon 470 is received by the user device 410, This will generally be the result of the user entering the transmission area of the beacon 470. As discussed above, the signal from the beacon 470 will include at least one beacon identifier, which can be used to identify the beacon 470 at S420. At S430, the user device 410 determines whether the criteria for activating the NFC capability of the user device have been met. Responsive to a determination that the activation criteria have been met, the NFC application of the user device 410 transitions from a passive state to an active state at S440. At S450, communication is established between the user device 410 and an NFC transmitting device (e.g., an RFID tag or POS device) disposed within the beacon transmission area. Additional NFC communications with other NFC transmitting devices can also be established. At S460, the user device 410 determines whether NFC deactivation criteria have been met. Responsive to the deactivation criteria being met, the NFC application of the user device 410 transitions from the active state to the passive state at S470.

Traditionally, only a single interaction result has been possible with an NFC device such as an RFID device: Information transmitted by the NFC device is received by the interacting device or it is not). This binary approach limits the functionality of NFC devices as information sources. It also presents a potential security issue in that any user can establish contact with an NFC device simply by bringing it into NFC communication range. The present invention provides for more complex interactions with NFC devices that can be used in conjunction with received NFC information to trigger actions by a user device.

In the methods of the present invention, a user of a mobile interface device may conduct a sequence of spatial interactions (sometimes referred to herein as “gestures”) between the mobile interface device and one or more NFC devices. In some embodiments the mobile interface device is configured to initiate NFC communication with an NFC device and to monitor the signal strength of transmissions received from the NFC device. Based on the signal strength, the mobile interface device can determine its relative proximity to the user device. This allows the mobile interface device to determine characteristics of the spatial interactions between the mobile interface device and the NFC device. These could include, for example, a nearest proximity to the NFC device, a length of time spent within a certain proximity range, or a speed of approach or withdrawal. In particular embodiments, such interaction characteristics can be compared to predetermined gesture sequence criteria to determine if a particular action should be taken.

In some embodiments of the invention, a mobile interface device may be configured for establishing a series of NFC communications with a plurality of NFC devices. In these embodiments, a gesture sequence may include a particular sequence of interactions with different NFC devices, any or all of which could include sequences of particular interaction characteristics as described above. In particular embodiments, the plurality of NFC devices may be physically disposed in a two dimensional or three dimensional array, and the sequence of NFC communications may be established with NFC devices selected to define a geometric pattern.

The following paragraphs describe certain gesture-based function-activation scenarios made possible by embodiments of the invention. While these descriptions refer to RFID devices, they are equally applicable to other NFC devices.

In the simplest communication scenario, brings the user device into communication range with an RFID tag. The RFID transmission is detected by the user device, which in turn activates a predefined function (e.g., launches a mobile function or application or performs some other action). In more complex scenarios, however, activation may require that certain qualifying gestures be made with the user device. Such qualifying gestures may involve one or more predefined gesture types. One type of gesture, referred to herein as a “tap”, is a short duration interaction in which the user brings the user device into communication range for a short time interval and then withdraws it. Accordingly, a qualifying “tap” gesture may be an RFID encounter in which the RFID transmission is received for less than a predetermined time interval. Activation criteria for the predefined function, then, could require that the user device/NFC device communication be a tap. A longer duration encounter would not trigger function activation. In applications where the user device can determine a relative distance from the RFID, a tap may additionally (or instead) require that the user device be brought within a close proximity to or in actual contact with the RFID tag.

In another gesture type, the user brings the user device into communication range of an RFID tag and holds it there for a longer period of time. This gesture type may be referred to as “touch and hold”. A qualifying “touch and hold” gesture may be established as an RFID encounter in which the RFID transmission is received for more than a predetermined time interval without interruption. Activation criteria for the predefined function, then, could require that the user device/NFC device communication be a touch and hold encounter. A shorter duration encounter would not trigger function activation. In applications where the user device can determine a relative distance from the RFID, a touch and hold may could require that the user device first be brought within a close proximity to or in actual contact with the RFID tag and then held within communication range for at least a threshold duration.

In some applications, different RFID encounter durations can be used to activate different functions. A tap, for example could cause a first function to be activated, while a touch and hold could be used to activate a second function. In some cases, additional hold duration ranges could be used to trigger activation of other functions.

Additional gesture types are available for user devices configured to monitor RFID communication signal strength. One example is a gesture in which the user brings the user device to within a particular distance range (proximity range) of an RFID tag and holds it there for at least a certain amount of time. This may be referred to as a “hover” gesture. Hovering may be determined based directly on a strength of the RFID signal or on a proximity derived from the signal strength. In some cases, a plurality of signal strength ranges representing different hover distances and/or hovering time intervals may be used to activate different functions.

Other gesture types may involve combinations of the simple gestures described above, the speed of approach or withdrawal of a user device relative to the RFID tag.

FIG. 5A illustrates a an NFC communication system 500 for implementing methods according to embodiments of the present invention. The system 500 includes a user device 510 (e.g., a mobile interface device) operable by a user and configured for communication with one or more NFC devices 580 (e.g., RFID tags or stickers).

The user device 510 includes an on-board data processor 511 in communication with a memory module 513, a user interface 514, a communication interface 512, and an NFC interface 519. The data processor 511 can include a microprocessor and associated processing circuitry, and can contain additional components, including processors, memories, error and parity/CRC checkers, data encoders, anticollision algorithms, controllers, command decoders, security primitives and tamper-proofing hardware, as necessary to perform the functions described herein. The memory 513 can be a read-only memory, write-once read-multiple memory or read/write memory, e.g., RAM, ROM and EEPROM, and the user device 510 can include one or more of these memories.

The user interface 514 includes a user input mechanism, which can be any device for entering information and instructions into the user device 510, such as a touch-screen, keyboard, mouse, cursor-control device, microphone, stylus, or digital camera. The user interface 514 may also include a display, which can be any type of device for presenting visual information such as a computer monitor, a flat panel display, and a mobile device screen, including liquid crystal displays, light-emitting diode displays, plasma panels, and cathode ray tube displays.

The communication interface 512 is in data communication with the data processor 511 and is configured to establish and support wired or wireless data communication over a communication network such as communication network 190 of FIG. 1. The NFC interface 519 is in data communication with the data processor 511 and is configured for establishing near field communication with any of the one or more NFC devices 580. Information received via the NFC interface 519 is forwarded to the data processor 511.

In various embodiments of the invention, the memory 513 may have stored therein one or more applications, each application comprising a plurality of instructions usable by the data processor 511 to carry out functions, and/or to conduct transactions between the user device 510 and merchant terminals, service providers, and transaction processing servers. These applications may include instructions usable by the data processor 511 to identify transaction events, store event data in the memory 513, and communicate event data to a transaction processor and/or a transaction monitoring system. Some applications may also include instructions relating to receiving and interpreting instructions from a transaction processor, transaction monitoring system, or other server.

In particular, the memory 513, has stored therein an NFC application comprising a plurality of instructions usable by the data processor 511 to establish communication with an NFC device 580 via the NFC interface 519 and to receive NFC information (including a device identifier) from one of the NFC devices 580. Each such communication may be referred to as an interaction. The NFC application further comprises instructions to determine one or more interaction characteristics for each such interaction. Such characteristics may include for example a duration of the communication, which may be defined as the length of time over which the user device can detect a signal from the NFC device 580. In some embodiments, the NFC application may be configured to determine a signal strength for the communication signal from the NFC device 580 and to monitor the signal strength through the duration of the communication. In such embodiments, the duration of the communication may be defined as the length of time over which the signal strength exceeds a threshold value. Other NFC interaction characteristics may include such measurable as the peak signal strength and the length of time the signal remains within a particular strength range. In some embodiments, the signal strength may be used to approximate the distance between the mobile user device 510 and the NFC device 580. In such embodiments, the distance/proximity between the two devise may be used as an interaction characteristic.

The memory 513 may have stored, a part of the NFC application or as a separate application, a gesture recognition application that is configured to monitor NFC interactions and interaction characteristics, recognize predetermined sequences of such interactions, and initiate appropriate transaction functions in response. For each NFC interaction, the gesture recognition application may compare the interaction characteristics to see if the interaction qualifies as a particular type of spatial interaction (e.g., a tap, touch and hold, or hover). Criteria for various gesture types may be preset or set by the user and stored in the memory 513. For example, the criteria for a qualifying hover gesture could be that the NFC signal strength be held within a certain range for a certain time interval.

The gesture recognition application may be configured, not only to recognize when an NFC interaction qualifies as a particular gesture, but to identify sequences of such qualifying interactions that meet predetermined criteria for initiating a transaction function in response to interaction with a particular NFC device 580 (or member of a particular group of NFC devices 580). Such criteria may include, for example, a requirement that a series of interactions with a single NFC device 580 match a specified order of specific gestures. For example, the predetermined sequence could be a tap followed by a second tap followed by a hover. If the user performs these gestures (i.e., causes the user device 580 to sequentially initiate communications with the NFC device 580 that qualify as a first tap, a second tap, and a hover), the criteria are met and an associated transaction function is initiated. In another example, the function initiation criteria could include a particular sequence of interactions with different NFC devices 580. For example, the predetermined sequence could be sequential interactions with a first NFC device 580 b, a second NFC device 580 c, and a third NFC device 580 a. The criteria could further require that a particular gesture be used to interact with each device (e.g. a tap for the first NFC device 580 b, a hover for the second NFC device 580 c, and a tap for the third NFC device 580 a.

In some embodiments, the function initiation criteria may also include limitations on the time between sequential interactions. For example, the criteria could specify that interactions with two separate NFC devices 580 a, 580 b must occur within a set time limit.

It will be understood that the user device 510 may be configured to carry out any number of gesture-conditional transaction functions with each transaction function being associated with a particular sequence of qualifying NFC interactions.

The one or more NFC devices 580 may be any NFC enabled transmitters. Each NFC device 480 may be specifically configured for communication of NFC information to NFC-enabled user devices. Each NFC device 580 has an associated NFC device identifier that is typically included in the transmitted NFC information. The device identifier is unique to the specific NFC device 580, and, once assigned, cannot be changed.

In some embodiments, multiple NFC devices 580 may be positioned adjacent one another in an array to facilitate interaction sequences that require interactions with more than one of the devices. In certain of these embodiments, the NFC devices 580 may be arranged in a particular pattern. In the exemplary array 581 in FIG. 5B, the NFC devices 580 are arranged to form rows and columns. While FIG. 5B illustrates a two-dimensional array, the NFC devices could also be placed in a three-dimensional array.

In particular embodiments, the NFC devices 580 are RFID tags. In some applications, such RFID tags may be used by a merchant in a retail environment. Merchants may, for example, position RFID tags in conjunction with product displays or in information kiosks within a retail store. In an illustrative scenario, RFID tags could be attached to a wall of a merchant display in the arrangement shown in FIG. 5B. In this scenario, a user device 510 having the above-described applications may have stored therein a transaction function associated with the merchant and function activation criteria associated with the merchant's RFID tags 580 aa, 580 ab . . . 580 ee. The function activation criteria could, for example specify that, in order to initiate the transaction function, the user device 480 must sequentially interact with four RFID tags along a square path 555 beginning with a specified RFID tag 580 bb. From the perspective of the application, the proper path will have been completed when the user causes sequential interactions with RFID tags 580 bb, 580 bd, 580 ed, and 580 eb followed by a second interaction with RFID tag 580 bb. Upon completion of the path, the user device 510 initiates the function, which could be, for example, transmitting a request to the merchant for product information or a discount.

FIG. 5C illustrates a flow diagram of a method M500 of activating a function in a mobile interface device according to an exemplary embodiment of the invention. At S510, the mobile interface device receives a sequence of NFC transmissions from one or more NFC transmitters. As previously described, the NFC transmissions are received as the result of NFC communication interactions between the mobile interface device and an NFC device or devices. The mobile interface device is configured to identify one or more NFC interaction characteristics for each such communication and to determine, based at least in part on these characteristics, whether the interaction qualifies as a predetermined gesture (i.e., exhibits certain predetermined spatial interactions). As previously discussed, NFC interaction characteristics may include, but are not limited to, communication duration, signal strength, duration of communication where signal strength is above a certain level or within a predetermined range, peak rate of change of signal strength, and nearest proximity of mobile device to NFC device.

At S520, the mobile interface device determines whether the sequence of transmissions meets predetermined function initiation criteria. The predetermined function initiation criteria may include requirements in relation to the order of a series of gestures for communications conducted with a single NFC transmission device. Alternatively, the criteria may include requirements in relation to an order of communications with different NFC devices. In some embodiments, the criteria may include a sequenced combination of gestures and NFC devices. In other embodiments, the criteria may include a limitation on the time between communications. The action S520 of determining whether the sequence of transmissions meets function initiation criteria may be repeated each time a new NFC communication encounter occurs.

If it is determined that a sequence of communication transmissions meets the criteria for initiating a predetermined function, the mobile interface device proceeds to execute the function. Typical functions that may be triggered based on a gesture sequence may include connecting to a merchant web page using a web-browser on the mobile device, initiating a purchase transaction, initiating a merchandise or service order, and requesting information about or a financial consideration (e.g., a discount) in relation to a merchant service or product. In some applications of the method M500, the NFC devices could be owned or controlled by the mobile device user. In such applications, potential functions might include initiating a communication (e.g., a call or text) initiating a payment, placing an order, or sending an operational instruction to another device or appliance.

It can be seen from the above disclosure, that the methods of the present invention allow the use of choreographed gestures in conjunction with a single NFC device (e.g., an RFID tag) or a plurality of NFC devices (e.g., RFID tags) to activate a function on a mobile device. This can provide a degree of flexibility not previously available in regard to the use of fixed NFC devices because it allows the functionality associated with an NFC device (or an array of NFC devices) to be changed without change to the NFC device (or device array). It can also allow multiple functions to be associated with a single NFC device or device array. In addition, it can provide an additional level of security in that it may require knowledge of a gesture sequence to execute a function on a user device, not merely the placement of the device within the communication field of an NFC device.

In some cases, customers belong to numerous loyalty and/or rewards programs. However, the related art does not provide simple ways for users to aggregate promotional data or track their loyalty programs from multiple merchants. Moreover, in the related art, RFID information is static or otherwise difficult to change. Accordingly, certain aspects of the present disclosure relate to the use of RFID tags (e.g., RFID stickers) to collect promotional or incentive-based data.

FIG. 6A is a system environment for implementing certain aspects of the present disclosure. In the system environment of FIG. 6A, a user device (e.g., user device 110, which may be a mobile device) operated by a user, an NFC device (e.g., an RFID sticker), a network (e.g., network 190), database 1 (e.g., service provider database system 130), database 2 (e.g., a second service provider database system 130), and one or more merchant databases (e.g., merchant database systems 150) may interact. The user may operate the user device to execute an RFID reader application, and the user may move the user device near the RFID sticker. The user device may read the RFID sticker and send the RFID information to database 1 over the network. Database 1 may recall (e.g. retrieve) the value for the RFID sticker from database 2 (e.g., over the network). Database 2 may receive updates to the RFID value from the merchant databases. In some cases, utilizing database 1 and database 2 provides a platform for partner aggregation and collaboration. For example, database 1 may be controlled by a first, and database 2 may be controlled by a partner merchant. In some cases, database 1 and/or database 2 may be controlled by one or more entities.

The RFID information may be static or otherwise difficult to change. For example, the RFID information may include an identifier for the RFID sticker. Functionality associated with the RFID sticker may therefore be determined based on mappings in database 1 or database 2. The merchant databases may set or change the functionality associated with the RFID sticker, for example, but accessing database 2 over the network. As a non-limiting example, the RFID sticker may be placed a first merchant location (e.g., at a store entrance). Upon entering the store, the user may tap the RFID sticker. The user device reads and sends the RFID information to database 1. Database 1 requests that database 2 indicate functionality is associated with the RFID sticker ((e.g., functionality set by the corresponding merchant database). Database 2 may notify database 1 about the associated functionality, for example, a 10% discount on purchases that data. Database 1 may relay that information to the user device. Thus, the user is notified about the daily discount. Merchant database may adjust the meaning (e.g., value or action taken) associated with the RFID sticker as often as desired (e.g., daily or weekly), and the same RFID sticker may therefore be mapped to different information or functionality.

FIG. 6B is an example flowchart of a method of the present disclosure. The user places the user device near the RFID sticker. The user device reads the RFID information and sends the RFID information to database 1 over the network. Database 1 recalls the value of the RFID from database 2. Database 2 be updated by merchant databases, thus changing the value of RFID.

In the prior art, the information transmitted by and the functionality associated with an RFID device are typically static (i.e., unchanging and unchangeable). Certain aspects of the present invention, however, enhance RFID functionality by allowing a system provider (or, in some cases, an individual user) to associate variable rules with a particular NFC device (e.g., an RFID device). The present invention also provides for the generation and transmission of variable information that can be used to authenticate communication between a user device and the transmitting NFC device.

FIG. 7A illustrates a rules-based NFC communication system 700 for implementing methods according to embodiments of the present invention. The system 700 includes a user device 710 (e.g., a mobile interface device) operable by a user and configured for communication with one or more NFC devices 180 (e.g., RFID tags or stickers).

The user device 710 includes an on-board data processor 711 in communication with a memory module 713, a user interface 714, a communication interface 712, and an NFC interface 719. The data processor 711 can include a microprocessor and associated processing circuitry, and can contain additional components, including processors, memories, error and parity/CRC checkers, data encoders, anticollision algorithms, controllers, command decoders, security primitives and tamper-proofing hardware, as necessary to perform the functions described herein. The memory 713 can be a read-only memory, write-once read-multiple memory or read/write memory, e.g., RAM, ROM and EEPROM, and the user device 710 can include one or more of these memories.

The user interface 714 includes a user input mechanism, which can be any device for entering information and instructions into the user device 710, such as a touch-screen, keyboard, mouse, cursor-control device, microphone, stylus, or digital camera. The user interface 714 may also include a display, which can be any type of device for presenting visual information such as a computer monitor, a flat panel display, and a mobile device screen, including liquid crystal displays, light-emitting diode displays, plasma panels, and cathode ray tube displays.

The communication interface 712 is in data communication with the data processor 711 and is configured to establish and support wired or wireless data communication over a communication network 790. The NFC interface 719 is in data communication with the data processor 711 and is configured for establishing near field communication with any of the one or more NFC devices 780. Information received via the NFC interface 719 is forwarded to the data processor 711.

In various embodiments of the invention, the memory 713 may have stored therein one or more applications each comprising a plurality of instructions usable by the data processor 711 to carry out functions, and/or to conduct transactions between the user device 710 and merchant terminals, service providers, and transaction processing servers. These applications may include instructions usable by the data processor 711 to identify transaction events, store event data in the memory 713, and communicate event data to a transaction processor and/or a transaction monitoring system. Some applications may also include instructions relating to receiving and interpreting instructions from a transaction processor, transaction monitoring system, or other server.

In particular, the memory 713, has stored therein an NFC application comprising a plurality of instructions usable by the data processor 711 to establish communication with an NFC device 780 via the NFC interface 719 and to receive NFC information from the NFC device 780. The NFC application may further include instructions to transmit some or all of the NFC information to a rule application server 760 over the network 790 via the communication interface 712. The NFC application may be configured to implement instructions received from the rule application server 760 in response to the NFC information transmission. As will be discussed, such instructions may be determined by the rule application server 760 based on rules associated with the particular NFC transmission device. In some embodiments, the NFC application may be configured to recognize a URL identifier in the NFC information and to cause the user device to initiate a web browser session and to navigate to the page specified by the URL identifier.

The memory 713 may also have stored thereon a transaction function association application. In some embodiments, this application may comprise a plurality of instructions to be carried out by the data processor upon establishment of communication with an NFC transmitting device. The instructions may, in particular, cause the device 710 to transmit received NFC information by the transaction processing device to a rules processor and receive a tag rule communication from the rules processor. The tag rule communication may include an instruction for the transaction application to carry out a transaction function associated with the tag identifier. Alternatively, if no transaction function has been assigned to the tag identifier, the rule communication may include a request to associate a new transaction function with the tag identifier. This request may include a plurality of function options and the transaction function association application may be further configured to cause the display of these options, receive a transaction function selection, and transmit a request response to the rules processor. In other embodiments, the transaction function association application may be configured to initiate an interactive session with the rules processor to specify a transaction function to be associated with the tag identifier.

The one or more NFC devices 780 may be any NFC enabled transmitter and/or receiver. Each NFC device 480 may be specifically configured for communication of NFC information to NFC-enabled user devices. Each NFC device 780 has an associated NFC device identifier that is typically included in the transmitted NFC information. The device identifier is unique to the specific NFC device 780, and, once assigned, cannot be changed. In addition to static information (i.e., information that does not change from communication-to-communication) such as the device identifier, the NFC devices 780 may be configured to include dynamic information in the transmitted NFC information. Such dynamic information is generated by the NFC device and is different for each communication and may be or include, for example, encrypted information. In some embodiments, the NFC device 780 may be configured to generate, for each new NFC communication, an encrypted verification block and include it with NFC information transmitted to a receiving device during the communication. As will be discussed, such an encrypted verification block may be used by a merchant system 150, a service provider system 130 or other system or server associated with the NFC device to verify the authenticity of the NFC device 780 and confirm user device 710 interaction therewith.

The rules-based NFC communication system 700 includes a rule application server 760, which may be part of a merchant system 150, a service provider system 130 or other system or server associated with the one or more NFC devices 780. The rule application server 760 includes a communication processor 762 configured for selective communication over the network 790. The communication processor 762 is configured, in particular, for communication with the user device 710 via the network 790 and for receiving NFC information received by the user device 710 in an NFC communication interaction with an NFC device 780 and forwarded by the user device 710. Upon receiving the NFC information, the communication processor 762 may forward the NFC information to an NFC identification (ID) processor, which is configured to determine the identifier of the NFC device 780. In embodiments where the NFC information includes an authentication component in addition to the NFC device identifier, the NFC information may be forwarded to an authentication processor 766. The authentication processor 766 is configured to use the NFC identifier and the authentication component to verify that an authentic interaction between the user device 710 and the identified NFC device 780 actually occurred. In particular embodiments where the NFC device 780 is configured to include a communication-specific encrypted verification block in the NFC information, the authentication processor 766 may be configured to decrypt the encrypted verification block and use the result to verify the authenticity of the communication. If the communication is deemed non-authentic, a message to that effect is returned to the user device 710.

Once the NFC device identifier has been determined and, if applicable, the NFC communication is authenticated by the authentication processor 766, the device identifier is passed to an NFC rules processor 768. The NFC rules processor 768 is in communication with a rules database 769 in which rules associated with the one or more NFC devices 780 are stored. The NFC rules processor 768 is configured to use the NFC identifier to determine if a rule is associated with that identifier. If so, the NFC rules processor 768 verifies that any additional criteria for rule application are met and takes action as specified in the rule. Rule-specified actions may be or include actions in relation to a user account associated with the user device 710 and/or actions to transmit information and/or instructions to the user device 710 (or other specified device associated with the user device 710 or the user account) over the network 790 via the communication processor 762. Instructions to the user device 710 may include instructions to display information on the user device 710, alter a setting of the user device 710, activate an application or function within an application on the user device 710, initiate an interactive communication session with the user device 710, initiate, complete or otherwise carry out a transaction, or provide an offer to the user.

The rules database 769 has stored therein records associating actions with NFC devices 780. Typically, a specified action is to be taken upon receipt of a notification of a communication between a user device 710 and an NFC device 780 for which the action is specified. In some embodiments, however, additional rule-application criteria may be specified. The action associated with a particular NFC device 780 may be assigned or changed at any time to reflect the desire of the owner or manager of the NFC device 780.

Embodiments of the above-described system 700 may be used to carry out various methods of the invention. In a particular example, the system 700 can be used to carry out a method of activating a transaction function in a transaction processing device (e.g., a mobile interface device or other user device) associated with a user's account with a particular merchant. FIG. 7B is a flowchart of an exemplary method M700A according to such an embodiment. At S710 of the method M700A, NFC transmitter information is received by a merchant server from the transaction processing device. This information will have been transmitted by the transaction device as a result of the transaction device having established NFC communication with an NFC transmitter device (e.g., an RFID tag) associated with the merchant. The received NFC information includes an identifier for the NFC transmitter device, which is determined from the NFC information by the merchant server at S720. In embodiments where the NFC information includes authentication information in addition to the NFC transmitter device identifier, the method M700A may include using the authentication information to authenticate the NFC communication between the transaction device and the NFC transmitter. Such authentication inhibits or prevents falsification of an NFC encounter. In such embodiments, the authentication information may be or include a data block encrypted using a symmetric key methodology such as that disclosed in U.S. application Ser. No. 16/205,119 filed Aug. 29, 2018, the complete disclosure of which is incorporated herein by reference. The action of authentication may include decrypting the encrypted data block as confirmation that the NFC information was actually generated by the identified NFC transmitter device.

At S730, the merchant server determines whether a transaction function has been associated with the NFC device. This may include querying the merchant's rules database to determine if there is a record assigned to the NFC device or if an assigned record indicates that a transaction function has been associated with the device. If a transaction function has been associated with the NFC transmitter device, the merchant server transmits an instruction to the transaction device to execute the transaction function at S740. in some embodiments, the transaction function may have been established by the merchant. In other embodiments, the transaction function may be established or selected by the user. By way of example, a merchant-established function could be an action to display product information, present an offer, or process a transaction. A user-established function could be an action to place a predefined order with the merchant, process a payment, display account or other information, or display product information. In some embodiments, the function could be to process a command to another device associated with the user or the user account.

In some embodiments, the method M700A may include an action of changing the transaction function associated with an NFC device. This action may, in some embodiments, take place in response to the occurrence of an event. In particular, the transaction function may be changed in response to the occurrence of an NFC communication between the transaction device and the NFC transmitter device and subsequent execution of the transaction function.

If the merchant server determines that no transaction function is associated with the NFC transmitter device, the merchant server may associate a transaction function with the NFC device. In some embodiments, this may include prompting and receiving a transaction function from the merchant. In other embodiments, this may include transmitting an association request to the transaction device or other device associated with the user. Either in response to such a request or through the establishment of an interactive communication session with the user, the merchant server may receive an action selection from the user, which the merchant server associates with the NFC device. The association is then recorded in the merchant's NFC rules database.

FIG. 7C illustrates a method M700B of initiating a transaction function in a transaction processing device (e.g., a mobile interface device or other user device). At S1710 of method M700B, NFC communication is established between the transaction processing device and an NFC transmitter device. Typically, this will be accomplished by the user bringing the transaction processing device within NFC communication range of (or in contact with) the NFC device so as to trigger the NFC communication application on board the transaction processing device. At S1720, the transaction processing device receives information (referred to herein as “NFC information”) from the NFC transmitter via the NFC communication. The received NFC information includes an identifier for the NFC transmitter device. In some embodiments, the NFC information includes authentication information in addition to the NFC transmitter device identifier. The authentication information may be or include encrypted information unique to the NFC device and the communication, which when decrypted by an authentication processor, serve to authenticate the NFC communication.

At S1730, the NFC information is transmitted by the transaction device to a merchant server configured for identifying the NFC device and determining a transaction function associated with the device. In some embodiments, the NFC information may comprise a network address that is used by the transaction device to establish an interactive communication session with the merchant server. At S1740, a rule communication from the merchant server is received by the transaction device. If a transaction function is associated with the NFC transmitter device, the rule communication may include instructions to execute the associated transaction function, whereupon the transaction device executes the transaction function at S1750. In some embodiments, the rule communication instructions request the user to confirm that the action is to be carried out prior to executing the transaction function.

If a transaction function is not associated with the NFC transmitter device, the rule communication may include a request to associate a function with the NFC transmitter device. The rule communication may further include an instruction to the transaction device to display a plurality of transaction functions to the user from which the user can select and enter a desired transaction function. The transaction device may transmit a response to the merchant server, the response including the user-selected transaction function to be associated with the NFC device. In some embodiments, this may be accomplished via an interactive exchange with the merchant server.

While traditional private label merchant credit lines (e.g., merchant branded credit cards) are often maintained by third-parties, which can be expensive and have limited fraud detection/authorization check points that lead to unnecessary costs, certain aspects of the present disclosure relate to enhancement of RFID functionality addressing these and other issues.

FIG. 8A is a system environment for implementing certain aspects of the present disclosure. In the system environment of FIG. 8A, a user, a user device (e.g., user device 110 or a mobile device), an NFC device (e.g., an RFID sticker), a network (e.g., network 190), and a server (e.g., service provider terminal 120). The user may operate the user device to execute an RFID reader application, and the user may move the user device near the RFID sticker. The user device may read and send the RFID information to the server over the network. The server may redemption/transaction values to the user device, and transaction may be performed utilizing the user device as a POS device.

In some cases, a plurality of RFID stickers may be dispersed throughout a merchant location (e.g., a store). The RFID stickers may, for example, be linked to discount/promotional codes or values, and/or specific items. Accordingly, as a user shops, selected items and discounts may be added to a user's virtual checkout “cart.” When a user scans a checkout RFID sticker (e.g., an RFID sticker at a designated checkout area), the scanning may trigger POS functionality of the user device. The user device may transmit the RFID information for the coupons and/or items to the server, and the server may inform the user device as to the transaction value. The user may then use the user device to finalize the transaction.

FIG. 8B is an example flowchart of a method of the present disclosure. The user places the user device near the RFID sticker (e.g., taps the RFID sticker). The user device reads and sends the RFID information to the server over the network. The server relays the tokenized redemption and/or transaction values to the user device based on the RFID information. The tokenized redemption/transaction is then completed on the user device. According to some aspects of the present disclosure, a user may access and utilize their merchant account at that particular merchant through their mobile device by tapping on an RFID-enabled checkout touchpoint. The touchpoint verifies the merchant location (i.e., is confirmed to belong to the merchant) and the transaction is processed within the user device. Accordingly, user/transaction authentication and merchant location remove the merchant's POS from the purchase flow and improve transaction security through enhancements to the user device and RFID functionality (e.g., providing multi-factor user authentication via the user device and merchant RFID).

FIG. 9 is a block diagram of an illustrative computer system architecture 900, according to an example implementation. As non-limiting examples, one or more of user device 110, service provider terminal 120, service provider database system 130, merchant terminal 140, merchant database system 150, and beacon 170 may be implemented using one or more elements from the computer system architecture 900. It will be understood that the computing device architecture 900 is provided for example purposes only and does not limit the scope of the various implementations of the present disclosed systems, methods, and computer-readable mediums.

The computing device architecture 900 of FIG. 9 includes a central processing unit (CPU) 902, where computer instructions are processed, and a display interface 904 that acts as a communication interface and provides functions for rendering video, graphics, images, and texts on the display. In certain example implementations of the disclosed technology, the display interface 904 may be directly connected to a local display, such as a touch-screen display associated with a mobile computing device. In another example implementation, the display interface 904 may be configured for providing data, images, and other information for an external/remote display 950 that is not necessarily physically connected to the mobile computing device. For example, a desktop monitor may be used for mirroring graphics and other information that is presented on a mobile computing device. In certain example implementations, the display interface 904 may wirelessly communicate, for example, via a Wi-Fi channel or other available network connection interface 912 to the external/remote display 950.

In an example implementation, the network connection interface 912 may be configured as a communication interface and may provide functions for rendering video, graphics, images, text, other information, or any combination thereof on the display. In one example, a communication interface may include a serial port, a parallel port, a general-purpose input and output (GPIO) port, a game port, a universal serial bus (USB), a micro-USB port, a high definition multimedia (HDMI) port, a video port, an audio port, a Bluetooth port, a near-field communication ((NFC) port, another like communication interface, or any combination thereof In one example, the display interface 904 may be operatively coupled to a local display, such as a touch-screen display associated with a mobile device. In another example, the display interface 904 may be configured to provide video, graphics, images, text, other information, or any combination thereof for an external/remote display 950 that is not necessarily connected to the mobile computing device. In one example, a desktop monitor may be used for mirroring or extending graphical information that may be presented on a mobile device. In another example, the display interface 904 may wirelessly communicate, for example, via the network connection interface 912 such as a Wi-Fi transceiver to the external/remote display 950.

The computing device architecture 900 may include a keyboard interface 906 that provides a communication interface to a keyboard. In one example implementation, the computing device architecture 900 may include a presence-sensitive display interface 908 for connecting to a presence-sensitive display 907. According to certain example implementations of the disclosed technology, the presence-sensitive display interface 908 may provide a communication interface to various devices such as a pointing device, a touch screen, a depth camera, etc. which may or may not be associated with a display.

The computing device architecture 900 may be configured to use an input device via one or more of input/output interfaces (for example, the keyboard interface 906, the display interface 904, the presence sensitive display interface 908, network connection interface 912, camera interface 914, sound interface 916, etc.) to allow a user to capture information into the computing device architecture 900. The input device may include a mouse, a trackball, a directional pad, a track pad, a touch-verified track pad, a presence-sensitive track pad, a presence-sensitive display, a scroll wheel, a digital camera, a digital video camera, a web camera, a microphone, a sensor, a smartcard, and the like. Additionally, the input device may be integrated with the computing device architecture 900 or may be a separate device. For example, the input device may be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.

Example implementations of the computing device architecture 900 may include an antenna interface 910 that provides a communication interface to an antenna; a network connection interface 912 that provides a communication interface to a network. As mentioned above, the display interface 904 may be in communication with the network connection interface 912, for example, to provide information for display on a remote display that is not directly connected or attached to the system. In certain implementations, a camera interface 914 is provided that acts as a communication interface and provides functions for capturing digital images from a camera. In certain implementations, a sound interface 916 is provided as a communication interface for converting sound into electrical signals using a microphone and for converting electrical signals into sound using a speaker. According to example implementations, a random-access memory (RAM) 918 is provided, where computer instructions and data may be stored in a volatile memory device for processing by the CPU 902.

According to an example implementation, the computing device architecture 900 includes a read-only memory (ROM) 920 where invariant low-level system code or data for basic system functions such as basic input and output (I/O), startup, or reception of keystrokes from a keyboard are stored in a non-volatile memory device. According to an example implementation, the computing device architecture 900 includes a storage medium 922 or other suitable type of memory (e.g. such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, flash drives), where the files include an operating system 924, application programs 926 (including, for example, a web browser application, a widget or gadget engine, and or other applications, as necessary) and data files 928 are stored. According to an example implementation, the computing device architecture 900 includes a power source 930 that provides an appropriate alternating current (AC) or direct current (DC) to power components.

According to an example implementation, the computing device architecture 900 includes a telephony subsystem 932 that allows the device 900 to transmit and receive sound over a telephone network. The constituent devices and the CPU 902 communicate with each other over a bus 934.

According to an example implementation, the CPU 902 has appropriate structure to be a computer processor. In one arrangement, the CPU 902 may include more than one processing unit. The RAM 918 interfaces with the computer bus 934 to provide quick RAM storage to the CPU 902 during the execution of software programs such as the operating system application programs, and device drivers. More specifically, the CPU 902 loads computer-executable process steps from the storage medium 922 or other media into a field of the RAM 918 to execute software programs. Data may be stored in the RAM 918, where the data may be accessed by the computer CPU 902 during execution.

The storage medium 922 itself may include a number of physical drive units, such as a redundant array of independent disks (RAID), a floppy disk drive, a flash memory, a USB flash drive, an external hard disk drive, thumb drive, pen drive, key drive, a High-Density Digital Versatile Disc (HD-DVD) optical disc drive, an internal hard disk drive, a Blu-Ray optical disc drive, or a Holographic Digital Data Storage (HDDS) optical disc drive, an external mini-dual in-line memory module (DIMM) synchronous dynamic random access memory (SDRAM), or an external micro-DIMM SDRAM. Such computer readable storage media allow a computing device to access computer-executable process steps, application programs and the like, stored on removable and non-removable memory media, to off-load data from the device or to upload data onto the device. A computer program product, such as one utilizing a communication system may be tangibly embodied in storage medium 922, which may include a machine-readable storage medium.

According to one example implementation, the term computing device, as used herein, may be a CPU, or conceptualized as a CPU (for example, the CPU 902 of FIG. 9). In this example implementation, the computing device (CPU) may be coupled, connected, and/or in communication with one or more peripheral devices, such as display. In another example implementation, the term computing device, as used herein, may refer to a mobile computing device such as a Smartphone, tablet computer, or smart watch. In this example implementation, the computing device may output content to its local display and/or speaker(s). In another example implementation, the computing device may output content to an external display device (e.g., over Wi-Fi) such as a TV or an external computing system.

In example implementations of the disclosed technology, a computing device may include any number of hardware and/or software applications that are executed to facilitate any of the operations. In example implementations, one or more I/O interfaces may facilitate communication between the computing device and one or more input/output devices. For example, a universal serial bus port, a serial port, a disk drive, a CD-ROM drive, and/or one or more user interface devices, such as a display, keyboard, keypad, mouse, control panel, touch screen display, microphone, etc., may facilitate user interaction with the computing device. The one or more I/O interfaces may be used to receive or collect data and/or user instructions from a wide variety of input devices. Received data may be processed by one or more computer processors as desired in various implementations of the disclosed technology and/or stored in one or more memory devices.

One or more network interfaces may facilitate connection of the computing device inputs and outputs to one or more suitable networks and/or connections; for example, the connections that facilitate communication with any number of sensors associated with the system. The one or more network interfaces may further facilitate connection to one or more suitable networks; for example, a local area network, a wide area network, the Internet, a cellular network, a radio frequency network, a Bluetooth enabled network, a Wi-Fi enabled network, a satellite-based network any wired network, any wireless network, etc., for communication with external devices and/or systems.

As used in this application, the terms “component,” “module,” “system,” “server,” “processor,” “memory,” and the like are intended to include one or more computer-related units, such as but not limited to hardware, firmware, a combination of hardware and software, software, or software in execution. For example, a component may be, but is not limited to being, a process running on a processor, an object, an executable, a thread of execution, a program, and/or a computer. By way of illustration, both an application running on a computing device and the computing device can be a component. One or more components can reside within a process and/or thread of execution and a component may be localized on one computer and/or distributed between two or more computers. In addition, these components can execute from various computer readable media having various data structures stored thereon. The components may communicate by way of local and/or remote processes such as in accordance with a signal having one or more data packets, such as data from one component interacting with another component in a local system, distributed system, and/or across a network such as the Internet with other systems by way of the signal.

Certain embodiments and implementations of the disclosed technology are described above with reference to block and flow diagrams of systems and methods and/or computer program products according to example embodiments or implementations of the disclosed technology. It will be understood that one or more blocks of the block diagrams and flow diagrams, and combinations of blocks in the block diagrams and flow diagrams, respectively, can be implemented by computer-executable program instructions. Likewise, some blocks of the block diagrams and flow diagrams may not necessarily need to be performed in the order presented, may be repeated, or may not necessarily need to be performed at all, according to some embodiments or implementations of the disclosed technology.

These computer-executable program instructions may be loaded onto a general-purpose computer, a special-purpose computer, a processor, or other programmable data processing apparatus to produce a particular machine, such that the instructions that execute on the computer, processor, or other programmable data processing apparatus create means for implementing one or more functions specified in the flow diagram block or blocks. These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means that implement one or more functions specified in the flow diagram block or blocks.

As an example, embodiments or implementations of the disclosed technology may provide for a computer program product, including a computer-usable medium having a computer-readable program code or program instructions embodied therein, said computer-readable program code adapted to be executed to implement one or more functions specified in the flow diagram block or blocks. Likewise, the computer program instructions may be loaded onto a computer or other programmable data processing apparatus to cause a series of operational elements or steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions that execute on the computer or other programmable apparatus provide elements or steps for implementing the functions specified in the flow diagram block or blocks.

Accordingly, blocks of the block diagrams and flow diagrams support combinations of means for performing the specified functions, combinations of elements or steps for performing the specified functions, and program instruction means for performing the specified functions. It will also be understood that each block of the block diagrams and flow diagrams, and combinations of blocks in the block diagrams and flow diagrams, can be implemented by special-purpose, hardware-based computer systems that perform the specified functions, elements or steps, or combinations of special-purpose hardware and computer instructions.

In this description, numerous specific details have been set forth. It is to be understood, however, that implementations of the disclosed technology may be practiced without these specific details. In other instances, well-known methods, structures and techniques have not been shown in detail in order not to obscure an understanding of this description. References to “one embodiment,” “an embodiment,” “some embodiments,” “example embodiment,” “various embodiments,” “one implementation,” “an implementation,” “example implementation,” “various implementations,” “some implementations,” etc., indicate that the implementation(s) of the disclosed technology so described may include a particular feature, structure, or characteristic, but not every implementation necessarily includes the particular feature, structure, or characteristic. Further, repeated use of the phrase “in one implementation” does not necessarily refer to the same implementation, although it may.

Throughout the specification and the claims, the following terms take at least the meanings explicitly associated herein, unless the context clearly dictates otherwise. The term “connected” means that one function, feature, structure, or characteristic is directly joined to or in communication with another function, feature, structure, or characteristic. The term “coupled” means that one function, feature, structure, or characteristic is directly or indirectly joined to or in communication with another function, feature, structure, or characteristic. The term “or” is intended to mean an inclusive “or.” Further, the terms “a,” “an,” and “the” are intended to mean one or more unless specified otherwise or clear from the context to be directed to a singular form. By “comprising” or “containing” or “including” is meant that at least the named element, or method step is present in article or method, but does not exclude the presence of other elements or method steps, even if the other such elements or method steps have the same function as what is named.

As used herein, unless otherwise specified the use of the ordinal adjectives “first,” “second,” “third,” etc., to describe a common object, merely indicate that different instances of like objects are being referred to, and are not intended to imply that the objects so described must be in a given sequence, either temporally, spatially, in ranking, or in any other manner.

While certain embodiments of this disclosure have been described in connection with what is presently considered to be the most practical and various embodiments, it is to be understood that this disclosure is not to be limited to the disclosed embodiments, but on the contrary, is intended to cover various modifications and equivalent arrangements included within the scope of the appended claims. Although specific terms are employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation.

This written description uses examples to disclose certain embodiments of the technology and also to enable any person skilled in the art to practice certain embodiments of this technology, including making and using any apparatuses or systems and performing any incorporated methods. The patentable scope of certain embodiments of the technology is defined in the claims, and may include other examples that occur to those skilled in the art. Such other examples are intended to be within the scope of the claims if they have structural elements that do not differ from the literal language of the claims, or if they include equivalent structural elements with insubstantial differences from the literal language of the claims. 

1. An automated method of activating a function in a mobile interface device using near field communication (NFC), the method comprising: receiving, by the mobile interface device, a sequence of NFC transmissions from one or more NFC transmitters, each NFC transmitter having an associated identifier and each NFC transmission being triggered by a spatial interaction between the mobile interface device and one of the one or more NFC transmitters; determining, by the mobile interface device, whether the sequence of NFC transmissions meets matching criteria for one of a plurality of predetermined transmission sequences; responsive to a determination that the sequence of NFC transmissions meets matching criteria for one of the predetermined transmission sequences, determining a predetermined function associated with the one of the predetermined transmission sequences; and initiating, by the mobile interface device, the predetermined function.
 2. An automated method according to claim 1 further comprising: determining at least one interaction characteristic for each spatial interaction, wherein the action of determining whether the sequence meets matching criteria is carried out using the at least one interaction characteristic for each spatial interaction and associated NFC transmission.
 3. An automated method according to claim 2 wherein the matching criteria includes a sequence of spatial interactions with a single NFC transmitter, each spatial interaction having one or more interact on characteristics falling within a predetermined value range.
 4. An automated method according to claim 3 wherein the one or more interaction characteristics includes a communication time interval over which the mobile interface device is within an NFC communication threshold.
 5. An automated method according to claim 3 wherein the one or more interaction characteristics includes a nearest proximity of the mobile interface device to the single NFC transmitter.
 6. An automated method according to claim 3 wherein the one or more interaction characteristics includes a rate of change of proximity of the mobile interface device to the single NFC transmitter.
 7. An automated method according to claim 3 wherein the one or more interaction characteristics includes a signal strength of the transmission from the single NFC transmitter.
 8. An automated method according to claim 2 wherein the matching criteria consists of a predetermined sequence of spatial interactions with a plurality of NFC transmitters.
 9. An automated method according to claim 8 wherein each spatial transaction has one or more interaction characteristics falling within a predetermined value range.
 10. An automated method according to claim 1 wherein the matching criteria includes a predetermined sequence of transmissions from a plurality of NFC transmitters.
 11. An automated method according to claim 1 wherein the predetermined function comprises instructions for at least one action of the set consisting of: connecting to a web page using a web-browser on the transaction processing device, initiating a purchase transaction, initiating a merchandise or service order, and requesting information about a merchant service or product.
 12. A mobile interface device, comprising: a data processor; a near field communication (NFC) interface configured to establish NFC communication with any of a plurality of NFC transmitting devices when the user interface device is placed within a communication range of said any of a plurality of NFC transmitting devices; a user interface comprising at least a user input device and a display; a memory accessible by the data processor, the memory having stored therein instructions for executing any of a plurality of device functions, each device function being associated with a different predetermined NFC transmission sequence, an NFC application including instructions for the data processor to receive an NFC transmission for each NFC communication established by the NFC interface, monitor sequential NFC transmissions to determine if a sequence of received NFC transmissions meets matching criteria for one of the predetermined transmission sequences, and if a received sequence of NFC transmissions meets the matching criteria for one of the predetermined transmission sequences, initiating the predetermined function associated with the matched predetermined transmission sequence.
 13. A mobile interface device according to claim 12 wherein the data processor includes a signal monitor configured to determine at least one transmission characteristic of each transmission received via the NFC interface.
 14. A mobile interface device according to claim 13 wherein the at least one transmission characteristic is signal strength.
 15. A mobile interface device according to claim 13 wherein the NFC application further includes instructions to receive the at least one transmission characteristic from the signal monitor, and the transmission sequence matching criteria includes, for each transmission in the transmission sequence, a range for the at least one transmission characteristic.
 16. A near field communication (NFC) system comprising: an array of NFC transmitting devices, each having an associated identifier; and a plurality of user interface devices each comprising a data processor; a user interface; an NFC interface configured to establish NFC communication with any of the array of NFC transmitting devices when the user interface device is placed within a communication range of said any of a plurality of NFC transmitting devices; a memory accessible by the data processor, the memory having stored thereon instructions for executing each of a plurality of device functions, each device function being associated with a different predetermined NFC transmission sequence, an NFC application including instructions for the data processor to receive an NFC transmission for each NFC communication established by the NFC interface, monitor sequential NFC transmissions to determine if a sequence of received NFC transmissions meets matching criteria for one of the predetermined transmission sequences, and if a received sequence of NFC transmissions meets the matching criteria for one of the predetermined transmission sequences, initiating the predetermined function associated with the matched predetermined transmission sequence.
 17. An NFC system according to claim 16 wherein the matching criteria for one of the predetermined transmission sequences require that the received sequence be received within a predetermined time limit, and the array of NFC transmitting devices is arranged to allow a user of one of the user interface devices to cause sequential interaction between said one of the user interface devices and a plurality of the NFC transmitting devices in the array within the predetermined time limit.
 18. An NFC system according to claim 16 wherein the plurality of the NFC transmitting devices form a geometric pattern.
 19. An NFC system according to claim 16 wherein the sequential interaction comprises a predetermined sequence of NFC transmitting device communications, each communication having a duration falling with a predetermined time interval.
 20. An NFC system according to claim 16 wherein each user interface device includes a signal monitor configured to determine a signal strength for each received transmission, and the data processor of each user interface device is configured to determine, for each received transmission, a proximity to the NFC transmitting device from which the received transmission is received based on the signal strength. 